Release Note v5.2.0

TronWeb supports building transactions locally for all APIs in transactionBuilder lib from this version. In the past, TronWeb will request the TRON node to build the transaction for each transaction type. And now, we just fetch the block header information and create the transaction data with protobuf. That is much safer because the transaction data is created in your local client. It is worth mentioning that the returned transaction data is compatible with previous versions.

For legacy support, we provide txLocal param for some APIs to set if you want to build transaction locally. As for some special API such as triggerSmartContract, when you trigger a pure or view function with triggerSmartContract, the http server in java-tron will response the constant contract result. Consequently, we keep the result and add the txLocal param. And it is highly recommended that you use it, as building triggerSmartContract transaction from remote servers will be deprecated in the future. By the way, if you are a DApp developer, you can import TronWeb in your DApp and create a transaction with your imported TronWeb which brings you better experience with the new features in 5.2.0. Here are the change logs:

• Transactions automatic built locally with protobuf
• Add txLocal: true param for triggerSmartContract, newTxID, alterTransaction, extendExpiration and addUpdateData APIs
• Consistent with the returned results of previous versions except triggerSmartContract has minor differences in abi
• Support the multi-signature of additional APIs including setAccountId, updateBrokerage, clearABI, updateAccountPermissions

Hope TronWeb makes your life easier.